<lit>OmniOutliner now requires Mac OS X 10.3.9 or higher. Removal of 10.2 support allowed us to simplify a good chunk of code and the vast majority of users are not using 10.2 any more. See our software update </lit>
<lit> client support. This allows you to embed editable content from other applications into your OmniOutliner document. More details below.</lit>
</run>
</p>
</text>
</values>
</item>
<item id="iqs5QA6YWqc">
<values>
<text>
<p>
<run>
<lit>Updated Tier-1 Localizations are now present (French, German, Spanish, Italian, Dutch, Japanese). If you see anything inside OmniOutliner that is not localized for one of these languages, it is a bug and we'd love to hear about it as soon as possible.</lit>
</run>
</p>
</text>
</values>
</item>
</children>
</item>
<item id="aUyHsSCPzJe" expanded="yes">
<values>
<text>
<p>
<run>
<lit>AppleScript</lit>
</run>
</p>
</text>
</values>
<children>
<item id="k1zuRK04dlO">
<values>
<text>
<p>
<run>
<lit>Fixed a performance issue with scripts that look up text values on rows for the purpose of merely reading them (notes, topics or other text columns). For example:</lit>
</run>
</p>
<p/>
<p>
<run>
<style>
<value key="font-fill">
<color r="0.5" g="0.5" b="0.5"/>
</value>
<value key="font-italic">yes</value>
</style>
<lit> first row of section 5 of front document whose note contains "Bob"</lit>
</run>
</p>
<p>
<run>
<style>
<value key="font-fill">
<color r="0.5" g="0.5" b="0.5"/>
</value>
<value key="font-italic">yes</value>
</style>
</run>
</p>
<p>
<run>
<lit>is now much faster. This eliminates progressive slowdown in the </lit>
<lit>Duplicating hierarchies of rows will no longer erroneously apply automatic level styles to those rows when the document has this setting disabled. We </lit>
<lit>Fixed a workaround that we had in place for a Cocoa scripting bug dealing with nested 'whose' specifiers that matched zero objects. Our over-zealous fix was causing a failure in the KGTD package's scripts.</lit>
</run>
</p>
</text>
</values>
</item>
<item id="iuQL5fLDF10">
<values>
<text>
<p>
<run>
<lit>Exporting documents via a specific XSL plugin is now easier/possible. In particular, this means you can control which of the many HTML variants are used when saving to a 'html' extension.</lit>
</run>
</p>
</text>
</values>
<note expanded="yes">
<text>
<p>
<run>
<lit>save TheDocument to "path" as (id of ThePlugin as string)</lit>
</run>
</p>
</text>
</note>
</item>
<item id="au9zLE1NAwj">
<values>
<text>
<p>
<run>
<lit>Enumerations are now accessible with the 'id' reference form.</lit>
<lit> client support. This allows you to embed editable content from other applications into your OmniOutliner document. For example, you might attach a little </lit>
}" name="LinkBack Item from OmniGraffle" expanded="yes"/></lit>
</run>
<run>
<style>
<value key="paragraph-alignment">center</value>
</style>
</run>
</p>
<p>
<run>
<style>
<value key="font-fill">
<color r="0.271739" g="0.271739" b="0.271739"/>
</value>
<value key="font-italic">yes</value>
<value key="font-size">11</value>
<value key="paragraph-alignment">center</value>
</style>
<lit>(use the Edit </lit>
</run>
<run>
<style>
<value key="font-fill">
<color r="0.271739" g="0.271739" b="0.271739"/>
</value>
<value key="font-italic">yes</value>
<value key="font-size">8</value>
<value key="paragraph-alignment">center</value>
</style>
<lit>‚ñ∂</lit>
</run>
<run>
<style>
<value key="font-fill">
<color r="0.271739" g="0.271739" b="0.271739"/>
</value>
<value key="font-italic">yes</value>
<value key="font-size">11</value>
<value key="paragraph-alignment">center</value>
</style>
<lit> LinkBack menu, or context menu, on the image to edit it in OmniGraffle)</lit>
</run>
</p>
<p>
<run>
<style>
<value key="font-fill">
<color r="0.271739" g="0.271739" b="0.271739"/>
</value>
<value key="font-italic">yes</value>
<value key="font-size">11</value>
<value key="paragraph-alignment">center</value>
</style>
</run>
</p>
<p>
<run>
<style>
<value key="font-fill">
<color r="0.795819" g="0.392859" b="0.405905"/>
</value>
<value key="font-italic">yes</value>
<value key="font-size">13</value>
<value key="paragraph-alignment">center</value>
</style>
<lit>You must have OmniGraffle Professional version 4 or later installed in order to activate this LinkBack attachment.</lit>
</run>
</p>
</text>
</values>
</item>
</children>
</item>
<item id="pHYKSRGlsjG" expanded="yes">
<values>
<text>
<p>
<run>
<lit>Import/Export</lit>
</run>
</p>
</text>
</values>
<children>
<item id="pq56vptsfRy">
<values>
<text>
<p>
<run>
<lit>We have switched from using Apache's Xalan XSL library to using libxslt. Libxslt is provided with Mac OS X as of 10.3.9, meaning our download size is now smaller and Apple gets to perform any necessary security updates on the XSL library instead of us. If you have custom XSL plugins, please try them out and let us know if any new problems appear (should be few, if any).</lit>
</run>
</p>
</text>
</values>
</item>
<item id="pnYpTxYb6w1">
<values>
<text>
<p>
<run>
<lit>Updated the plugin loading code to require that the plugins have unique bundle identifiers and switch to using the bundle identifier as part of the AppleScript identifier for the plugin-defined file type.</lit>
</run>
</p>
</text>
</values>
</item>
<item id="cEdFNUIexAd">
<values>
<text>
<p>
<run>
<lit>We now refuse to load XSL plugins that have executable code. This was never used for nefarious purposes, but it seems like a good idea.</lit>
</run>
</p>
</text>
</values>
</item>
<item id="cAGWY0KnNuV">
<values>
<text>
<p>
<run>
<lit>Fixed another case of plain text file attachments getting grabbed by QuickTime.</lit>
</run>
</p>
</text>
</values>
</item>
<item id="jI6czkhlXeX">
<values>
<text>
<p>
<run>
<lit>Enumerations now have unique identifiers that are stored in the file.</lit>
</run>
</p>
</text>
</values>
</item>
<item id="k6XIq53kDB2">
<values>
<text>
<p>
<run>
<lit>RTF export will no longer reserve space for handles if all the handle types are empty in the RTF Export preferences. Likewise, space will no longer be reserved for the checkboxes if all the checkbox options are empty.</lit>
</run>
</p>
</text>
</values>
</item>
<item id="bq4wjWL2ZQK">
<values>
<text>
<p>
<run>
<lit>Fixed issue where inadvertently added control characters could break exporting via our XSL plugins. OmniOutliner will now discard these characters.</lit>
</run>
</p>
</text>
</values>
</item>
<item id="buA8h5qN8R2">
<values>
<text>
<p>
<run>
<lit>Fixed issue with <xsl:comment> breaking the dynamic HTML export.</lit>
</run>
</p>
</text>
</values>
</item>
<item id="lSdTbkkZ2qZ">
<values>
<text>
<p>
<run>
<lit>Some fixes to HTML export for row numbering.</lit>
</run>
</p>
</text>
</values>
</item>
</children>
</item>
<item id="bMyabRAfs4-" expanded="yes">
<values>
<text>
<p>
<run>
<lit>Interface</lit>
</run>
</p>
</text>
</values>
<children>
<item id="pgkK9AUjRbm">
<values>
<text>
<p>
<run>
<lit>Adding a new row will no longer cause the mouse pointer to appear briefly.</lit>
</run>
</p>
</text>
</values>
</item>
<item id="fx1BzKCBG6R">
<values>
<text>
<p>
<run>
<lit>Keyboard navigation in preference panes is more consistent.</lit>
</run>
</p>
</text>
</values>
</item>
<item id="igNNGOhouGS">
<values>
<text>
<p>
<run>
<lit>Split out older release notes into a different file.</lit>
</run>
</p>
</text>
</values>
</item>
<item id="aGfU-icLkoy">
<values>
<text>
<p>
<run>
<lit>Added a Welcome document to help new users find out more information about OmniOutliner. This will appear automatically once and from then on you can access it from Help </lit>
</run>
<run>
<style>
<value key="font-size">9</value>
</style>
<lit>‚ñ∂</lit>
</run>
<run>
<lit> Welcome.</lit>
</run>
</p>
</text>
</values>
</item>
<item id="dPp7RSGgJ0R">
<values>
<text>
<p>
<run>
<lit>The Style Attribute inspector normally merges a group name and attribute name when the group only contains a single item. But, this could result in attribute names being clipped. Now, we only merge the two items if doing so would produce no clipping.</lit>
</run>
</p>
</text>
</values>
</item>
<item id="asgPCBX1Sxa">
<values>
<text>
<p>
<run>
<lit>Fixed 'enter' key handling on PowerBooks so that it again toggles between editing the note and row text.</lit>
</run>
</p>
</text>
</values>
</item>
</children>
</item>
<item id="eSoznHdBQMj" expanded="yes">
<values>
<text>
<p>
<run>
<lit>Spotlight</lit>
</run>
</p>
</text>
</values>
<children>
<item id="d74lxiwjdv-">
<values>
<text>
<p>
<run>
<lit>If an error occurs while indexing an OmniOutliner 3 document, a message will not be logged to the console. We don't know of any such errors making it out into the Real World‚Ñ¢, but this seems like a good idea. Let us know if you see any such messages.</lit>
</run>
</p>
</text>
</values>
</item>
</children>
</item>
<item id="dF9bwEFkmOv" expanded="yes">
<values>
<text>
<p>
<run>
<lit>Stability</lit>
</run>
</p>
</text>
</values>
<children>
<item id="iZi-kTeypAZ">
<values>
<text>
<p>
<run>
<lit>Fixed a crash when deleting and undoing a row that matches an existing batch find.</lit>
</run>
</p>
</text>
</values>
</item>
<item id="j5x3yqoO2jb">
<values>
<text>
<p>
<run>
<lit>After a successful save, we now cancel any pending autosave. Also, after a 'save to' operation, we no longer cancel any pending autosave on the source document.</lit>
</run>
</p>
</text>
</values>
</item>
<item id="a1XiHNDMemt">
<values>
<text>
<p>
<run>
<lit>Fixed a problem with mouse tracking in the style attributes inspector that could capture your mouse.</lit>
